[Malleability] Update mapBackData to use generics and implement BackData #7098
+144
−129
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…low/flow-go into UlianaAndrukhiv/7073-mapBackData-generic-refactoring
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Close: #7073
It is part of the broader refactoring effort referenced in EPIC #6646.
Context:
This PR refactors the existing MapBackData to separate it from using
flow.Identifierandflow.Entityby introducing generics.The
MapBackDatanow uses generic type parameters:Key(K) is constrained with comparable, ensuring that it supports equality checks.Value(V) is defined as any, allowing flexibility.This PR also updates the
adjustparameter for theAdjustandAdjustWithInitmethods to return not only the new adjusted value but also the new key for that value.Tests and usages have been updated accordingly.